(evil-define-motion evil-fwd-sexp (count)
:type inclusive
(setq count (or count 1))
(unless (zerop count)
(goto-char
(save-excursion
(condition-case err
(let ((opoint (point)))
(cond
((> count 0)
(condition-case nil
(forward-sexp)
(error (forward-char)))
(when (> (point) (1+ opoint))
(setq count (1- count)))
(forward-sexp count)
(backward-char)
(point))
(t
(setq count (- count))
(forward-char)
(condition-case nil
(progn
(backward-sexp)
(setq count (1- count)))
(error (backward-char)))
(backward-sexp count)
(point)))))))))

(evil-define-motion evil-bwd-sexp (count)
:type inclusive
(evil-fwd-sexp (- (or count 1))))

Some points to add:

@Combining Commands
vfa; can also be written as v2fa just to demonstrate that f(ind) and t(o) also take numeric arguments (think of M-2 for the rest of Emacs). Also most other (motion) commands take numeric arguments.

Evil supports text objects so you can also define your di$KEY to delete inside such a text object. (For more see evil-commands.el)

@Defining normal mode commands
From the Merge Request emerged the evil-leader package, to be found here: https://github.com/cofi/evil-leader (I also added it now to the plugins list on emacswiki/Evil)

@My dotfiles
cofi-evil.el depends on cofi-util.el and the cl package, if you copied code and something fails look there ;) (well and the other `require'd packages)

evil-{define,declare}-key support also more than one definition at a time to keep your key bindings clean.

I mapped my CapsLock to Ctrl and use `jk' to exit insert mode (look for cofi/evil-maybe-exit) because this way using other Emacs packages (that sadly never heard about Evil) is way easier. You can also exit insert state via C-[ but that's quite cumbersome.

Last but not least: Evil is discussed at the vim-emulation mailing list also accessible via gmane: http://news.gmane.org/gmane.emacs.vim-emulation that surely should also go into the 'Where you can learn more' list ;)

The reason it's important to think about this is that using some Emacs motion commands while in Evil normal/visual mode results in unexpected or incorrect (usually, in the off-by-one sense) behavior due to the different underlying model of the cursor positioning. Sexp-motion commands are the key culprits here, but there might be others. Ideally, I'd like to see Evil compensating for this difference in behavior (see this discussion), but it's somewhat subtle and I personally don't have a clear conception of how one would do this in such a way as to preserve behavior that's sensible for Emacs without breaking Vim commands.

(Alternatively, someone could tell me how to navigate through code in Evil effectively without resorting to sexp-motions. I have found them to be very handy, and I know seasoned Emacs users that swear by them for any sort of code navigation.)

One minor possibly pedantic point: I would argue that there is no asymmetry in how Emacs handles selections. The key difference between Emacs and vi is that in emacs the position is always "between" characters where in vi it is "on" a character. For this reason, I have always set the cursor in Emacs to be a vertical bar to highlight this aspect. When using evil, I keep the cursor as a block. The difference positioning between the modes is then made visually clear.

Thanks again!