Does ASC 2 remove unnecessary activation objects?

Question

The release notes for ASC 2 say: "Reduces function overhead by removing unnecessary activation records. "
Does this actually happen?  Can someone give a code example that shows this?
I've tried the braindead cases where you'd think this would happen (empty with, empty anonymous function, empty try), but the resulting bytecode doesn't seem to show this optimization.  I'm using the optimize and remove-dead-code flags. 
Am I missing something obvious?  I'm sure I'm using ASC 2, because I can put code above a package block.

Answer 1

Activation objects should no longer be generated for a try/catch (empty or not).  I just tried out a simple example, and ASC2 did not generate an activation object for the method containing the code:
try{x = 10;}
catch(e){print(e)}
How are you testing if the activation object is present?  Do you have some sample try/catch code that is generating an activation object that you could post?  
Activation objects are still generated for 'with' and nested functions, so if you have one of those in your method you will still see the activation object.