executable name sucks

**Current Candidate(s)**

* `bingrep` (no rename)
* `binocular`
* `bing`

---------

`bg` cannot be used without path prefix because of `bg` for job backgrounding in bash/posix.

so we need to choose a better one. i'm thinking two letters (lets jump on the grep shortname bandwagon renaissance we're in the middle of).

Some candidates:

0. binocular
1. binlens
1. ~~od (ObjDump)~~
2. ng (biNGrep)
3. ig (bInGrep)
4. bd (BinDump)
5. bing (BINGrep)
6. bgrep

Or also any other name :P

No files, tests, or entry points are named. Start by reviewing the current executable name, the listed candidates, and the repository references to the executable; the work is done when the project has an agreed name and its executable references consistently use it.

Written by the indexing model from the issue text.