One difficulty with debugging strategies or indicators is that you often want to step through the code to see what's happening on a specific bar.
Most debuggers internally don't have a way to set conditional break points that, for example, depend on CurrentBar > 211.
Maybe those tools you describe have a way to solve it. TickZOOM which will be released soon has a simple feature to type in a "break at bar" number to the GUI.
It then generates a conditional break point on that specific bar before any processing of any ticks or setup for that bar occurs.
Then you can set a break point in your strategy code and continue.
At that point you're stepping through code for your specific bar.
It's an extremely convenient feature just from using it myself.
Wayne