Dosbox 0.65 works better than 0.63 for:
WC2 (smoother at same # of cycles, able to turn cycles up higher. DosBox's joystick support is also improved. Game speed was consistent during fights, instead of speeding up/slowing down depending on the # of objects on screen like I was used to)
WC3 (smoother at same # of cycles, able to turn cycles up higher, smooth on my system in high detail now (at least for the first mission))
WC
riv (WAY better than 0.63. Loading time between dialogue sections COMPLETELY eliminated at full speed on my system. Intro cutscene absolutely perfect - even better than on my P133 running DOS. Space is smooth as silk)
WC:Armada (smoother at same # of cycles, able to turn cycles up higher. I went from 19000 cycles in 0.63 to 22000 cycles in 0.65. At first I thought the frame limiter must be broken, but then I found out in #wingnut it really was supposed to be that fast. Lasers fire 8 shots per second, who knew?)
Of course, HCl hasn't made a NetBios version of 0.65, so the NetBios multiplayer modes won't work. I didn't have any success with pg in two instances of dosbox on the same machine (after the game starts, the two immediately have an unrecoverable sync error), but supposedly they improved IPX support so maybe it would work correctly if they were on separate machines.
Actually, there's something I haven't tried yet... I'm going to have to do a little experiment when I get home today...
(These are the only games I've tried so far. And this was on back on Saturday, so I don't remember what I set the cycles to for most of the games.)
Also, I have a fairly powerful machine (3.4 GHz P4). I would actually expect bigger improvements in lower end systems, since the extended update notes mention some significant optimizations to the drawing code, which seems to be a bigger chunk of the cpu load on slower systems, in my experience.
One last thing. I forget whether it was Privateer or Armada, but one of those used to complain about ems unless you set ems=false in the .conf file. No longer.