Initially, I also thought that D+D was only displaying CPU usage, because of the processes being run under it.
However, the difference between running commands through D+D and directly through CMD is noticably
I did a test with PAR2 just recently. By running the command thrugh D+D, it took 48,8 sec to get from 0,1 to 0,5 percent. The same process took 36,2 sec by running the command directly.
D+D fluctuates between 0 and 50% cpu usage (50% is one core). Actually, it was at 0% CPU usage about 60% of the time. The difference is also noticeably, in the sense that the percentage of work done, increases more rapidly when run directly.
Also, if the process were 'hiding' under D+D, it makes no sense that moving/clicking the D+D window would instantly drop CPU-usage to zero.
Something is definitely wrong.