I think something was wrong with the configuration of the environment variables for profiling.
Executing
VSPerfCLREnv /sampleon
via command line did the trick. Afterwards profiling the CPU worked with the command line tools as well as in Visual Studio.
More details on how to use the profiler from the command line can be found here.