Can you tell us why you need this in addition to bounds biasing?

If you don't know about bounds biasing, see here:
https://code.google.com/apis/maps/documentation/javascript/places.html#places_autocomplete

I find it works really well.

I find I have the same issue with the bounds biasing that it doesn't respect the country bounds.  Using the above link and the example code: https://code.google.com/apis/maps/documentation/javascript/examples/places-autocomplete.html 

If I start typing "auck" for Auckland New Zealand, or "per" for Perth it shows up Perth, and Peru whereas if you look in the bounds it's only Sydney.  Those other results shouldn't be coming up first or even at all if the bounds are restricting to where the viewport is.  The same applies if you specify the bounds too.

Bounds biasing seems to work if you make a really small boundary within the country you want to restrict to but it still brings up countries as preference, so for Canberra, Australia you have to type in Canb to get past Canada being the #1 entry. 

jquery options all seem much slower so a native solution would be nice, please. 

Country filtering is now supported for Autocomplete:

http://googlegeodevelopers.blogspot.com.au/2012/05/faster-address-entry-with-google-places.html

Brilliant. Thanks for this. 

yes, thank you very much. 

Hi,
Is there any hope to get support for multiple countries ? Be able to get results for both Australia and New Zealand  would be useful.
Do you plan to add this feature ?
Thank you