please use the new thread (C# wrapper 2.0 - RELEASE) in the future for discussions about the wrapper !

@MasterQ32
The idea with assigning vectors isn't a good idea. If vectors were immutable, then assigning them this way would be plausible. But as they are now they are mutable thus the syntax you would propse would mean that the vector object would be REPLACED by the new vector object and that is simply not the case - you only want it to assume the same value - not the same reference to the unmanaged memory.

about wrapping all functions - this is after all a wrapper - which has the advantage that it basically should only wrap methods - not implementing them. Thus through wrapping the functions you have the exact same behaviour as without the wrapper !
You can always build your own 'optimized' vector utility class !

ref/out aren't the same as the delegates !
There are only a handful of situations where they are needed - for example with a slider (panel element) ! The value of the variable you want to be modified isn't modified while the function you call the arguments with is executed ! The values are modified at not yet known points in time (when the user moves the slider) thus ref/out doesn't work - because you can't keep (variable references !) with a ref/out after the method has returned !