I've been using the layout loading feature and it has been working great.  As I add features more panels and documents can exist that can get stored in a users layout.  I've been looking into optimizing some of this so layouts don't take as long to load.

One of the things I discovered is that each time I use the NDockingFrameworkState.Load(mylayoutfile) method I see entries like this in the console:

'MyApplication.vshost.exe' (Managed (v4.0.30319)): Loaded 'mrfahxlx'

in searching the internet I came across this article: http://www.ticklishtechs.net/2010/07/

It seems as though dynamic assemblies are created and loaded by this operation.  After reading the article it suggests there may be performance implications with this approach as well as a potential memory leak as this operation is performed multiple times (as would occur in an application like mine where the user is encouraged to change layouts for different feature sets).

What is the optimal way of loading layouts and should I be concerned with the above issue with this Nevron method?  I'm on Win7 using build 11.12.14.12.