Yes, I can see this, too, with at least

$ fossil version
This is fossil version 1.18 [df9da91ba8] 2011-07-13 23:03:41 UTC

Also the transcript is very interesting:
<verbatim>
$ ./tst.sh
project-id:
server-id:
admin-user: phaeton (initial password is "41ba40")
ADDED  some-file
New_Version:
-rw-------  1 phaeton  users  0 Aug 22 11:27 some-file
After rm: some-file is not there.
repository:
local-root:
server-code:
checkout:     2011-08-22 15:27:20 UTC
parent:       2011-08-22 15:27:20 UTC
tags:         trunk
comment:      added some file (user: phaeton)
MISSING    some-file
After fossil update: some-file is not there.
repository:
local-root:
server-code:
checkout:     2011-08-22 15:27:20 UTC
parent:       2011-08-22 15:27:20 UTC
tags:         trunk
comment:      added some file (user: phaeton)
MISSING    some-file
UPDATE some-file
--------------
updated-to:   2011-08-22 15:27:20 UTC
tags:         trunk
comment:      added some file (user: phaeton)
"fossil undo" is available to undo changes to the working checkout.
repository:
local-root:
server-code:
checkout:     2011-08-22 15:27:20 UTC
parent:       2011-08-22 15:27:20 UTC
tags:         trunk
comment:      added some file (user: phaeton)
EDITED     some-file
fossil: there are unsaved changes in the current checkout
</verbatim>
Look at the last two lines. After doing nothing more than an update, fossil thinks some-file has been EDITED where it's not. It's an empty file, just like the one that has been added.