This is just a reminder to check if our current asv suite is sufficient to detect the memory footprint improvements related to fixing gh-811, and if not we should add a peak memory benchmark or two that are sensitive to that suite.

That said, it is quite common not to have CI tests for memory leaks, even in quite large projects, so we can probably delay the actual mem profiling code for a little bit as long as we fix soon-ish.