What version of gpg2 for Windows (gpg2 --version)? Who built that binary?

That's gpg2 2.0.12, installed as part of gpg4win 2.0.1 (binary version installed).

PLease do a gpg --version which gives teh exact version number of the binary you
are actually using. Is that the gpg4win downloaded from ftp.gpg4win.org?

yes, it's the official binary release from ftp.gpg4win.org.

C:\Documents and Settings\pbr>gpg --version
gpg (GnuPG) 2.0.12 (Gpg4win 2.0.1)
libgcrypt 1.4.4
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: C:/Documents and Settings/pbr/Application Data/gnupg
Unterstⁿtzte Verfahren:
╓ff. Schlⁿssel: RSA, ELG, DSA
Verschlⁿ.: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128,

CAMELLIA192, CAMELLIA256

Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Komprimierung: nicht komprimiert, ZIP, ZLIB, BZIP2

That is a funny bug. Well not really funny but hard to believe if you don't
consider some of the patches we apply in gpg4win. In gpg4win 2.0.1 is a patch
which adds 2 addtional status code macros. The patch obviously patches the
sources (common/status.h). The patch then triggers a make rule to rebuild
status-codes.h from status.h. Due to the vpath build and a bug in the makefile
we end up with two status-codes.h files. This explains why we have two ideas of
the STATUS_ATTRIBUTE macro's value, which are off by 2.

The problem exists also in 2.0.13 if you do a vpath build and change certain
source files.

I fixed this in the SVN but we can't do a quick fix for gpg4win. We plan to get
an gpg4win RC out this month which will include the fix.