There's a cute trick with the xor operator
I haven't really used modulus for anything besides rand(), and to be honest I would be tripped up on a modulus question. XOR operators I have used, and do use on a regular basis, but the mechanics behind xor I would only consider asking if I'm hiring for a high level position that has a lot of technical work behind it that would benefit from knowing how xor stuff works(e.g like a video codec). I try to steer clear of nitty gritty stuff like this because people are coming in knowing there competing against a lot of people so they come in scared.
I have been doing programming now for 17 years and professionally for 10, it really wasn't until I went to college and talked to people in the game industry that I was able to land my first gig. I'm entirely self taught(I really just went to college to do the meet and greet stuff), and I remember when I was first out of high school I got a dry interview at Square Enix. The guy asked me what was global scope and local scope; I knew what scope was but never heard that term before. Needless to say I botched up the interview, but now that I actually have to do interviews I try to take that experience into account.
Their are a lot of veterans in the game industry(my field anyway) who are entirely self taught like myself that haven't heard various terms like scope(until someone brings it up) but they know what it is. This is why I try not to be a term nazi and if someone doesn't know something, I give them the chance to look it up. If they see the term and go drr and from there look away from the screen, and tell me exactly what it is I'm just fine with that. But you would be surpised on how many college graduates can't look stuff up, and I know for a fact they probably haven't done some parts of what I need them to do(just becuase a lot of game programming stuff isn't taught in any school), and if they can't figure it out I can't hold someones hand through the work.
Again it finds programmers that paid attention in school, doesn't mean they have good logic, just good retention .
C++/CLI has its own ECMA standard distinct from the ISO C++ standard, it is not designed by the same comittee, it has a different syntax, a different compiler, it compiles for a different platform.
CLI I don't think is used enough and have enough practical usage to be taught as its own course. Personally, I wish CLI would just go away, it really clusters up a codebase .
To each his own, but I personally like the steer away from stuff like that because as I said just above that shows more retention rather than logic, and since a lot of things I need my employess to get done aren't taught in school I really try and group logic testing and ability to research something in one section of the interview. This why I ask someone how to do something I know isn't taught in school, and they can outline and do research on what needs to get done as quickly as possible odds are there pretty logical.
Before that if they know polymorphism, pointers, etc I know they can at least program, so I try not to focus to much on if they can program or not. I want to find someone that can think out side the box. One other question I ask is, since I always look for someone that knows C# and C++, I ask them how would automate hooking up managed and unmanaged code without using CLI or Com.