How can I ensure that a Message Loop in Win API doesn't use the CPU when no messages are available