I found a memory allocation when changing the active subgraph in a very common usage pattern
this allocates memory because of the lambda variables scope capture.
Attached the stack trace from a deep profiling in unity where it allocates 160 B for every sub tree change.