Develop scheme for handling nested messages types (objects)

[Jason-Abbott]

Like issue #2, this is handled in Go ORMs using annotations (tags) to indicate which child structs should be stored as an independent key-value pair matched to its parent in the codec.

The initial approach will probably do nothing -- just enode children with parents. We need to add use cases illustrating pros and cons of flattening the message structure.