Gary Borton

Would your definition of reachable include additional files? If not, we could create a `PrivateMochaWrapper` with all the internals chainable + easily readable, and then change the public api functions...

This should definitely be reusing the header/footer/and line logic from `output` rather than reimplementing. Also, I'm looking at `output`/`outputSingle` and see that both return a string rather than logging.... @tedivm...

It might be best to standardize the profiler's memory object (I've avoided documenting this as I didn't want it to be public api, but it's pretty stable now) and then...

This is basically happening because you're attempting to wrap something that's already being wrapped... It was added as a convenience function to prevent you from double wrapping functions and inflating...

@wtfrank are you getting this without calling any of the `.registerX` functions?

Do you know if you're registering anything that might be wrapping `Room.toString()`?

It's unclear to me why you want want to turn this off... but it is certainly doable. I think in the most ideal world there is no config/options. How do...

I've been meaning to add this by default, and probably log a warning if it thinks you might have accessed memory before enabling the profiler. This can be done pretty...

This might have some value in terms of checking specific areas of code, but I think that profiling functions is more important. It's more likely that you have an expensive...

Hmmm, I'm not sure that I like removing the sub calls by default. This'll definitely impact current users. I wonder if that could be optioned via a top-down vs bottom-up...