Make the 32k []byte pool in memz safer
Problem to solve
In !540 (merged) we added a global pool of 32k []byte
objects. The way it is used right now is safe, but it's a bit dangerous, because a section of the code must never read memory beyond what they wrote themselves.
Is there a way to safely reuse the memory without exposing previous writes?