Right now, if you are designing the pages you load yourself, providing an SVG version of the fonts to be used, is indeed an option (just as we do in the WPF WebControlSample), though you should be careful with copyrights regarding the use of some fonts (SVG is an open format).
Offering an option to force all fonts to be rendered using Skia with smoothing instead of the native OS fast-path, is a suggestion we've already added to our tracker.
The issue has been discussed before: http://answers.awesomium.com/questions/271/ The operating system or bindings are not related to this behavior. It's a native Awesomium behavior. As mentioned in posts you must have already read (http://answers.awesomium.com/questions/600/) .NET bindings don't use any .NET specific technique to render fonts.
We hope to have an option for this available, by the next update.