Reconsider DefaultEffectiveStatement definition

Our current definition of DefaultEffectiveStatement (and declared statement by extension) requires users to manually parse the value to correlate it to the actual value.

What we really would like to say is that both these have a bound value, which is bound the parent type – i.e. the bracket is EffectiveStatement<Object>, specialized to Uint16 for uint16 types.

Since we are required to parse the argument when a statement is defined, this needs some more thought as to the inference mechanics – i.e. before we can successfully create the statement we need to have its parent statement perform type inference to resolve the base type.