Agreed not smarter. The `LocationSerializer.LocationPointer` is similarly dumb. For the latter, it's known about by the serialize/deserialize mechanism so things putting/getting to the storage deal with real Location/Entity instances.

No need to do anything else about it in this pull request; just need to be aware that the `feature/storage2` has the same concept in another piece of code.