Does not support ref/out parameters

[H1M4W4R1]

Implementation of that feature will be quite complicated, because it would require to encapsulate those params into additional class structure that would store it inside during Aspect Processing execution and return it afterwards.

Another way is to rework the encapsulation system to amend original method body adding execution start and end calls into that body, however it would require to do this also on return statements, which is also quite hard because it requires to scan whole method body for those statements.

[H1M4W4R1]

Possible solution
MethodInfo.Invoke uses object[] as parameter container. object[] is an reference type and while executing method it's data is also changed while method has ref and out parameters. The data is not changed if it's modified inside executed method and param is not marked as out/ref. Thanks to this it allows us to move data array from executing encapsulated method to separate variable that is then provided to encapsulator and set parent variables with out/ref basing on that array.

[H1M4W4R1]

Moved to #7
Partially fixed in #7, needs testing.