[storm] Find out why global memory allocations start taking much longer after a while

[perlun]

By adding #150, I came to the conclusion that memory_allocate seems to have some peculiarities going on, which sometimes degrades its performance by a factor of 500 to 1000 - i.e. the system goes from having reasonable real-time performance (making it possible to play mod files with #145) to being completely sluggish and barely usable.

This screenshot illustrates the problem ("Last memory allocation took" is the key):

I believe the only reasonable way to solve this is by fixing #4 using the approach suggested in #4 (comment) and I will see if it can be done with a reasonable effort.

[perlun]

Note: the screenshot is inverted because of a bug on my behalf; it's the global memory allocations that are taking an enormous amount of time, not the other way around.

[perlun]

Regarding the timings, I'm not sure how accurate they are. (We need better timers I think, especially ones that work in virtualized scenarios also. Perhaps using HPET or something would make sense; HPET in particular is blacklisted on Linux for some Intel chips though, so it might not be a great fit after all. 😒)