[Feature] Profile Memory

[RiftLurker]

It's currently not possible to profile Memory deserialization cost, because the Profiler accesses (and therefor deserializes) Memory when checking if it should be profiling.

This can be solved in one of the following ways:

• Add an option to profile Memory deserialization
• Provide a function wrapper that doesn't check if the profiler is enabled

[gdborton]

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 simply by timing access to Memory very early on in the profiler's logic, logging if that access takes < ~2ms.