Dining Philosopher correctness
Dinning Philosophers

How should I improve my solution for Dining Philosopher's problem?

Well first implementing the Dining Philosophers problem would be good. This is an interesting problem you implemented but its not the classic Dinning Philosophers
The issue here is that in your implementation each philosopher tries to grab any two forks. In the classic implementation each philosopher is assigned two specific forks (though each is shared with another philosopher).
The other issue is that you have a single lock for the whole table. In reality you should have a lock on each fork. Just because philosopher one is grabbing fork one does not stop philosopher three grabbing fork three.
Also if a philosopher fails to get either fork, then it must give up all forks and think for a random period.
Code Review
Prefer initializer list. Also you don't need a temporary v in the constructor.
Dining()
{
    vector&lt;int&gt; v = { 1,2,3,4,5 };
    chopsticks = v;
    count = 0;
}

Dining()
    : chopsticks{ 1, 2, 3, 4, 5}
    , count(0)
{}

Use RIAA.
If you have code that looks like
InitSomething

// Stuff

UnitSomething

Then you should have an object that handles the InitSomething in the constructor and UnitSomething in the destructor.
In this:
    arbit.lock();

    // STUFF

    arbit.unlock();

Should look like this:
    std::lock_guard&lt;std::recursive_mutex&gt;   lock(arbit);
    // STUFF

Don't use dynamic allocation when automatic variables will work
Dining* philosophers = new Dining();

This should be:
Dining   philosophers;