Definitely, I'm still not sure it's giving the 100% accurate size in memory, however it is definitely a step up from sys.getsizeof.

I've fixed the bug causing the above, thank you for the call out!