Which memory names cause you issues, Mike?
Anything that involves
my memory!

I just quickly looked at this again. I think the two primary gotcha's I have had was that
$CTRIO_004_C2F1.fReg1 is hard to distinguish from
$CTRIO_004_C2F1.iReg1 primarily due to the lower case i and f getting lost in the R in the proportional font (unlike in this font where they are easier to tell apart. $CTRIO_004_C2F1.fReg1 $CTRIO_004_C2F1.iReg1)
I nicknamed them to help, e.g. Head4_CTRIO_Hz and Head4_CTRIO_Cnt which brings up the second one I have snagged on - If I don't use the scaling when setting up the CTRIO, then $CTRIO_004_C2F1.iReg1 = $CTRIO_004_C2F1.iReg2 and Reg1 seems natural. If I later realize I wanted to get a scaled speed from the count, then Reg2 is the raw count and Reg1 the rate and well... That one took me a little while as it was on a D0-06, but I got bitten again on the one I have pulled these examples from.
So I reckon I have an issue with
1)Readability on the i and f
2)I would probably prefer SCL and RAW rather than Reg1 and Reg2
3)I would rather raw was always Reg1
With all that said, this is mostly preference and I was merely pointing out that the fly-by on the CTRIO in the video was perhaps too "All ya gotta do", so I got hung up on that rather than getting the main video theme.

AutomationDirect has a ton of videos on how to use Do-more!. This particular set (The Do-more! Way) was designed to show users how the system configuration works and why it is designed the way that it is, hence the name.
If you really want to know how to set up a CTRIO 2, try taking a look at these videos.
Yes, but I think I mentioned annoying music and such (pointless ads since I am almost guaranteed to be a user already.) Pet peeve.