VTune can be incredibly useful, if you are programming in Java or C/C++/Asm. It can identify bottlenecks in code by sampling where in you program the processor is every n ns as well as performing static analysis of the output of your compiler to help tune important sections of code.

As far as a debug/crack/hack tool, it is not particularly useful. It does disassemble on the fly to show the 'hot spots' of the target code, but there is no useful way to save this information, let alone stop it an examine registers/codeflow/etc.

But as they say, if all you have is a hammer, everything else is a nail (paraphrase)