<exclude>
Debugging class useful for finding memory leaks.
If you think you are leaking instances of a class, but are having a hard time distinguishing valid instances from invalid ones in a memory profiler, create a reference to a MemoryMarker object from your leaked object at a point just before the object should terminate.
For example, to find leaked instances of WPFCustomControls.MaxRibbonControl, we can add a reference to a new MemoryMarker during HandleUnloaded. We can then identify the roots for the leaked MaxRibbonControl instance by looking for the MemoryMarker instance.