Follow up, that same RELEASE mode .NET hello world app shows 153MB in the VMMAP tool used in the blog post, so i's not entirely because of the configuration.
I think the issue is that the tool is showing you what is mapped into the address space of the process which may not use any memory. It could be mapped files or copy on write pages etc.
When I started that post I used the DEBUG build because I (mistakenly) thought that was the only was to get the pdb symbols, but I was wrong about that.
I think that I'll update the post with RELEASE mode screenshots, because having DEBUG ones just confuses things. Very few people (no-one?) will be running a DEBUG version of the CLR in real-world situations, so it's a bit confusing to use it.
I think the issue is that the tool is showing you what is mapped into the address space of the process which may not use any memory. It could be mapped files or copy on write pages etc.