It sounds like the real problem is that the debugger (windbg) isn't smart enough to handle inline strings. If they had used a more powerful debugger they wouldn't have been confused enough to write a blog post about it.
They're just bytes in memory and there's nothing stopping you from putting whatever you want in the code section (as long as you don't try to execute it).