It'd be nice to add some sort of memory allocation/deallocation profiling support for allocations made within the runtime (through the FreeingBumpHeapAllocator), and maybe write a script so that the data can be easily exported into something like my Bytehound for analysis.

(This could probably be worked around by profiling the native runtime, but that's not ideal since 1) the native runtime is going to go away anyway, 2) it'll be extra noisy so it'd be harder to analyze and 3) it might not exactly match with what happens in an actual WASM runtime considering e.g. the native environment will be 64-bit and WASM is 32-bit, etc.)