View needs to call constructor on super
Removing unnecessary overhead
Using hasOwnProperty is better for user keys on objects we control
Key in obj check not appropriate for user supplied keys
Properties set with set should not be accessed with bracket
Using a dedicated object for value storage

Without this, we are limited in the key names that we can accept from users.  And because of compiler renaming, we don't know ahead of time what the limitations are (e.g. the key 'a' may clobber the 'set' method).
Add method for getting keys
Merge pull request #217 from tschaub/safer-object

Allow ol.Object to be used with arbitrary keys.  Add a getKeys method.