Do you think it's worth having `used_memory` explicitly be a `uint64_t` instead of relying on `size_t`? I'm trying to imagine a platform with a 32-bit `size_t` where the ODB would ever end up caching more than `size_t` total data - is such a thing even possible?