Reflection utility

To speed things up, we use caching
This is a global cache holding member types
This way we should reflect only once per class/member in the application lifetime (assuming that member types don't change)
Some operations like tweening use this cache
The cache could be cleared manually anytime

Sets the specified value on a given object

Member wrapper cache
A member wrapper creation is the result of reflecting the property/field of a class
Since this should be done no more than once during the application lifetime, we use the cache
This cache has additional methods forgetting/setting values having 2 parameters: type and property

Class used for proxying a member via type + string member name

The wrapper around the class member
The main idea behind this approach is that whis wrapper could be cached
and reused per class basis

Compares properties