<p>Windbg fans claim that it is quite powerful and I tend to agree. But when it comes to debugging STL containers, I am always stuck. If the variable is on the stack, the <code>!stl</code> extension sometimes figures it out, but when a container with a complex type (e.g. <code>std::vector&lt;TemplateField, std::allocator&lt;TemplateField&gt; &gt;</code>) is on the heap or part of some other structure, I just don't know how to view its contents.</p>

<p>Appreciate any tips, pointers.</p>

I often find debugger support for STL data types inadequate.  For this reason I'm increasingly using
logging frameworks and logging statements
.  I used to think that these are for people who can't use a debugger, but I now realize that they offer real value.  They allow you to embed portable debugging knowledge in your code and maintain it together with the code.  In contrast, work you do in the debugger is typically ephemeral.