For any direct-equivalency type definitions (i.e. non-struct, e.g. "type foo string"), any references to the defined type (foo) will be replaced with the underlying type (string) at parse-time, as if the annotation referred to the underlying type (string) all along. This prevents the model section from being cluttered with empty (foo) definitions.
Merge pull request #42 from polyglot-jones/equivalency-typedefs

For any direct-equivalency type definitions (i.e. non-struct, e.g. "type foo string"), ...