Looks good enough to me for a non-public API. I expect more contentious arguments if this is ever made public, since the problems remain very tricky. Only a VM that monitors memory "hot spots" can really get this right ... but the VM we have is already named "hotspot" ...