I like the GetStored answer, which would work perfect in my case to make certain the child is stored properly.  

In my real life example, the original save used %Save(0) and therefore did not save somethingelse.myNewProperty, but it was still displaying the correct value when I was (ref it directly) and writing it out, as it was getting it from memory.

Thank you everybody for your answers. My question here would be, why use class method instead of regular method in this case? 

If you don't want it to have exposure to outside world, simply make it a regular method within your class, which is going to be private (I believe) by default and use as many as you need privately, while still have an outside entry point if needed with non private class method.

I guess what would be the benefit to use class method vs regular method here?  

I see myself small benefit to make something originally class method [private] vs regular method - in case in some point in the future of your application, you need to change the ability to get to the method from the outside and remove the private tag.