The property, which is intended to behave as a field as much as possible, in this case continues to look like a field but doesn't act like one. That means that switching transparently between a field and a property (the holy grail of good properties) will silently break code.
Some other discussion in property topic made me wonder if enforcing const on getter non-ref return values makes sense.
