With server Tight 1.2.9 :
No problem. I've been using this one for some time with a very efficient ZLibRaw codec.

With server Tight 1.3beta4 :
The server randomly crashes when using other codecs that Tight (also when using TightVNC as client).
The server sends corrupt data when using CoREE encoding, which also causes TwinVNC crashes.
This problem was fixed by adding preventive clipping before encoding.

With server Tight 1.3beta5 :
No server crashes with ZLibRaw encoding. Data is still corrupt with CoREE, but TwinVNC uses alkaround.
Looks like the server sometimes "forgets" to refresh certain screen areas, also happens with TightVNC client.

With server RealVNC 4 :
No problems found with current version of TwinVNC.

With all servers :
They all have some problems with some refreshed parts! This problem can be reproduced with TwinVNC as much as with any Windows VNC Viewer.

Tip: Just click within the modified area so that the server can notify it has been changed and send appropriate data to the client.