Two proposed solutions for iOS TOS not allowing runtime code

I understand that loading runtime code is prohibited by Apple iOS TOS.  Fine.  I am willing to compile all my resources into one big SWF to get the job done to meet the legal requirements.

However, in our setup (and I imagine for many projects) it's not possible to do this easily.  Different SWFs are owned by different teams - it's actually part of what makes the Flash ecosystem so great and the workflows so powerful.

The easiest solution is embedding all my assets, which I assumed would work but it didn't, becasue the [Embed] tag uses Loader, which under iOS nixes embedded actionscript.

Porposed solution #1:

It seems to me to be in the spirit of the TOS to allow actionscript code in SWFs that are embedded into the iOS actionscript code, because all of this code was available at compile-time and at packaging-time.

    [Embed(source="myAnim.swf")]

      private var anim:Class;

Code in the embedded myAnim.swf should be allowed.  Technically the only reason it isn't is because embed's result in a Loader - merely an implementation detail.  If this isn't acceptable...

Propsed solution #2:

What about a new feature to meet this need: [LinkedEmbed] that results in a statically linked class compiled at compile-time and not Loaded at runtime?

    [LinkedEmbed(source="myAnim.swf")]

      private var anim:Class;

Thanks for your time and consideration,

-Jeff