[REQ] Tracking memory allocations #1269

Description

In a complex program built with warp, with arrays being stored in multiple classes, and some of them being "true" arrays while others are zero-copy views, it can become complicated to keep track of all memory allocations and understand where the memory usage comes from. A great addition would be a debugging tool that tells you what arrays are currently allocated at a given point, and with what size.

Context

I was seeing unexpectedly high memory consumption when profiling my code, and after inspecting the more obvious suspects I was still missing some memory. I could try an experimental version of that feature, and it pointed me directly to the allocations I hadn't been accounting for, so that was very helpful.