This page describes all problems, tasks and solution approaches regarding tracing of method invocations in the same thread.

...

This is not suitable for asynchronous methods.  

@Stefan and Patrice: Am i right here?

(Also see continues sending in IS advanced notes for better understanding)

New approaches /

...

idea

Possible approachIdea:

Analog to the container method, but the sending of information would be triggered  for example after each 5 method closure. (Ask if the size sending strategy is just that.)
To distinguish the method invocations done by the current thread from this done by other threads, each thread\runnable would get an ID(Remember thread pools and runnable reuse).On each hook, the Id of the currentThread would be acquired. So it could be saved when an method was executed by what thread.
(How much overhead would this generate?)

Questions / Possible Problems

...