There’s not really any news as such because the timings are as they are supposed to be. I would like to clarify some things. Can I ask what you meant by “ANTS cuts all the time used for the framework functions away”. This isn't true - the profiler records all time taken for methods if you are profiling with the default option.
Well it is true if you look at the Time(s) column (not the Times with childs column!). In Ants 3 the Time(s) column showed the complete execution time of a method including framework calls but excluding your own child functions (that is exactly what we are interested in - how long takes the longest method and how can I optimize them).
Surely you can now use the "Time with childs column" but there is a big problem associated with it -> first I have to walk down the whole tree to find the functions which only has framework calls left and no other child functions - thats very time consuming in our case.
In ANTS 3 I simply sorted by Time(s) and got the longest performing methods without having to worry about any child functions.
But since ANTS 4 sees all the internal framework calls as child functions you really don't see how long a specific method takes you in the Time(s) column... so thats why the Time(s) is mostly below 0.001s anyway and not of any use at all...
I hope you understand what we need and why for that Ants3 is much better now to use .
Hopefully you can bring an option back in Version 5 to also calculate the framework functions in the Time(s) column again, because as of yet we don't use Ants 4, even though its much faster and better overall.