I'm using version 4.6.652, and mine looks like:
PROCESS - PRIVATE BYTES -- PEAK PRIVATE BYTES
ashDisp.exe - 1,796K -- 7,868K
ashMaiSv.exe - 2,544K -- 8,076K
ashServ.exe - 17,496K -- 23,744K
ashWebSv.exe - 4,520K -- 6,552K
aswUpdSv.exe - 408K -- 408K
= 26,764K -- 46,648K
You can see from my peak bytes that at some point it was using a lot of memory.
But probably from playing Desert Combat or something.
By using Task Manager, its Memory Usage stat just reads the Working Set value
which is smaller than the Private Bytes.