This is either a bug with SFML and VC++ 2010, or SFML WinXP 32-bit. Moving the executable that gives the Access Violation error to my mac, or my Win7 computer results in no errors, and it works fine.
I don't see the implied bug.
Just because an executable happens to display the behaviour you expect on some specific system does not mean that it has no bugs and is not prone to undefined or implementation-defined issues. Just because moving some executable to some arbitrary system causes it to execute in a manner that you expect does not mean that it will always do so.
