Currently, this involves digging through each entry in the Types tab and viewing the root paths one at a time.
By providing the dominant root referrer in the Types tab, it would also be easy to create a report (via Copy) that covers a bit of both ends of memory leaks -- what is leaked, and which are the main roots... actually, it is this Reporting need that triggered this post (the root cause
