There have been a number of ideas on how to improve memory profiling

## Related Resources

A nice competitive analysis from Lewis - "Web vs C++ Memory Leaks " https://docs.google.com/document/d/1HBpe5VbziP3WnOpfUKnM87GSblF69v40Mh-Uzduw3G0/edit# (google only)

samccone's garbage talk: https://www.youtube.com/watch?v=fCLiYVk4rPQ

memory audits:
* https://github.com/twosigma/beaker-notebook/pull/1714
* https://github.com/google/material-design-lite/issues/761
* https://github.com/tastejs/todomvc/issues/1333
* https://github.com/tastejs/todomvc/pull/1441#issuecomment-145748163
* https://github.com/tastejs/todomvc/pull/1337#issuecomment-112821596

## Ideas

* Sampling heap profiler
  * Get line-level data to achieve feature parity with XCode Leaks
* Restore dominators view (minor)
* Productizing sam's workflow: timeline + memory counters, along with GCs. Associating stacks to heap (thus allocation). Finding retainers.
* Snapshot exploring: Better exposure of the hover preview of objects. That all objects can be logged to console and explored in $0.


I'm sure there have been a million more ideas and inspirations. Let's use this issue to log 'em.