Good article. Handy way to monitor CPU.

But one improvement I would like to see is a way to find which process is causing the CPU hit.

It may not be always SQL Server process. Or atleast it should say SQL usage % and other process usage %. Another improvement can be some information to figure out what internally caused the CPU pressure within SQL Server, if SQL was consuming the most of CPU. For addressing these, I prefer DMVs.